Skip to content

Support test automation exclusion annotations in JUnit4 - #12940

Open
calvinbayer wants to merge 8 commits into
masterfrom
codex/junit4-automation-exclusions
Open

calvinbayer wants to merge 8 commits into
masterfrom
codex/junit4-automation-exclusions

Conversation

@calvinbayer

@calvinbayer calvinbayer commented Oct 19, 2026 •

Copy link
Copy Markdown

What Does This Do

Add public @NoAutoRetry and @PreventFailureSuppression annotations and JUnit4 support. The exclusions independently control Datadog retries and quarantine/disabling while preserving framework-owned skips, explicit retries, Test Impact Analysis selection, and backend-assigned management tags.

Motivation

Let developers protect individual critical tests from Datadog automation. Each annotation also exposes a TAG constant for the native tag/group integrations in the later framework PRs.

Additional Notes

First PR in the Java framework stack. Shared declaration resolution, execution policy, reporting, and public annotation Javadocs live here. The declaration resolver uses cached annotation types and native tag constants; JUnit4 supplies the same source and category metadata to skip decisions and reporting.

Validation: focused declaration-resolver, public API, execution-policy and event-handler tests; the instrumented JUnit4 suite; formatting checks; and public API Javadoc generation. The regressions verify independent flags, disabled/quarantined/attempt-to-fix assignments, blocking protected failures, annotation telemetry, and TIA forced-run reporting.

@calvinbayer calvinbayer added type: feature Enhancements and improvements comp: ci visibility Continuous Integration Visibility tag: ai generated Largely based on code generated by an AI or LLM labels Oct 19, 2026
@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - sbt-scalatest

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 59.60 58.86 $\color{red}{\blacktriangle}$ +0.74 57.69 $\color{red}{\blacktriangle}$ +1.91 94/423
agentEvpProxy 59.29 n/a n/a n/a n/a -

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - nebula-release-plugin

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 37.45 38.67 $\color{green}{\blacktriangledown}$ -1.22 37.91 $\color{green}{\blacktriangledown}$ -0.46 48/212
agentless 37.03 37.91 $\color{green}{\blacktriangledown}$ -0.88 37.15 $\color{green}{\blacktriangledown}$ -0.12 48/213
agentlessCodeCoverage 45.61 46.30 $\color{green}{\blacktriangledown}$ -0.69 46.30 $\color{green}{\blacktriangledown}$ -0.69 48/212
agentlessLineCoverage 56.92 57.69 $\color{green}{\blacktriangledown}$ -0.77 56.55 $\color{red}{\blacktriangle}$ +0.37 47/211

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@datadog-datadog-prod-us1-2

This comment has been minimized.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - netflix-zuul

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 92.56 93.23 $\color{green}{\blacktriangledown}$ -0.67 91.39 $\color{red}{\blacktriangle}$ +1.17 48/212
agentless 86.02 84.36 $\color{red}{\blacktriangle}$ +1.66 82.69 $\color{red}{\blacktriangle}$ +3.33 48/212
agentlessCodeCoverage 101.14 99.00 $\color{red}{\blacktriangle}$ +2.14 97.04 $\color{red}{\blacktriangle}$ +4.10 48/212
agentlessLineCoverage 117.60 116.18 $\color{red}{\blacktriangle}$ +1.42 113.88 $\color{red}{\blacktriangle}$ +3.72 47/212

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - reactive-streams-jvm

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 21.00 22.54 $\color{green}{\blacktriangledown}$ -1.54 22.54 $\color{green}{\blacktriangledown}$ -1.54 50/247
agentless 18.32 19.59 $\color{green}{\blacktriangledown}$ -1.27 19.59 $\color{green}{\blacktriangledown}$ -1.27 49/239
agentlessCodeCoverage 17.70 20.39 $\color{green}{\blacktriangledown}$ -2.69 20.39 $\color{green}{\blacktriangledown}$ -2.69 48/239
agentlessLineCoverage 24.63 27.52 $\color{green}{\blacktriangledown}$ -2.89 27.52 $\color{green}{\blacktriangledown}$ -2.89 29/160

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - pass4s

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 16.80 10.97 $\color{red}{\blacktriangle}$ +5.83 10.54 $\color{red}{\blacktriangle}$ +6.26 48/214
agentless 13.12 10.97 $\color{red}{\blacktriangle}$ +2.15 10.33 $\color{red}{\blacktriangle}$ +2.79 49/213
agentlessCodeCoverage 21.82 17.73 $\color{red}{\blacktriangle}$ +4.09 17.73 $\color{red}{\blacktriangle}$ +4.09 45/194

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - heliboard

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 10.20 9.92 $\color{red}{\blacktriangle}$ +0.28 9.92 $\color{red}{\blacktriangle}$ +0.28 47/211

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - sonar-kotlin

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 14.51 13.94 $\color{red}{\blacktriangle}$ +0.57 13.67 $\color{red}{\blacktriangle}$ +0.84 48/224
agentless 12.46 12.37 $\color{red}{\blacktriangle}$ +0.09 12.37 $\color{red}{\blacktriangle}$ +0.09 48/224
agentlessCodeCoverage 16.34 16.04 $\color{red}{\blacktriangle}$ +0.30 15.72 $\color{red}{\blacktriangle}$ +0.62 48/224
agentlessLineCoverage 17.62 18.08 $\color{green}{\blacktriangledown}$ -0.46 17.73 $\color{green}{\blacktriangledown}$ -0.11 47/223

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - jolokia

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 97.15 97.04 $\color{red}{\blacktriangle}$ +0.11 97.04 $\color{red}{\blacktriangle}$ +0.11 52/232
agentless 93.12 93.23 $\color{green}{\blacktriangledown}$ -0.11 91.39 $\color{red}{\blacktriangle}$ +1.73 50/229
agentlessCodeCoverage 101.90 101.00 $\color{red}{\blacktriangle}$ +0.90 101.00 $\color{red}{\blacktriangle}$ +0.90 51/230
agentlessLineCoverage 102.64 103.04 $\color{green}{\blacktriangledown}$ -0.40 103.04 $\color{green}{\blacktriangledown}$ -0.40 62/258

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - okhttp

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 18.75 19.20 $\color{green}{\blacktriangledown}$ -0.45 19.20 $\color{green}{\blacktriangledown}$ -0.45 50/229
agentless 18.66 18.82 $\color{green}{\blacktriangledown}$ -0.16 18.82 $\color{green}{\blacktriangledown}$ -0.16 50/231
agentlessCodeCoverage 22.06 21.65 $\color{red}{\blacktriangle}$ +0.41 22.09 $\color{green}{\blacktriangledown}$ -0.03 50/235
agentlessLineCoverage 37.75 37.91 $\color{green}{\blacktriangledown}$ -0.16 37.91 $\color{green}{\blacktriangledown}$ -0.16 48/226

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@dd-octo-sts

dd-octo-sts Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite Status
Startup 🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results
Scenario Candidate master Δ (95% CI of mean)
startup:insecure-bank:iast:Agent 14.79 s 14.68 s [-0.1%; +1.7%] (no difference)
startup:insecure-bank:tracing:Agent 13.61 s 13.64 s [-1.1%; +0.6%] (no difference)
startup:petclinic:appsec:Agent 17.15 s 17.11 s [-0.7%; +1.2%] (no difference)
startup:petclinic:iast:Agent 17.03 s 16.51 s [-1.3%; +7.5%] (no difference)
startup:petclinic:profiling:Agent 16.71 s 16.76 s [-1.3%; +0.8%] (no difference)
startup:petclinic:sca:Agent 17.06 s 16.42 s [-0.3%; +8.0%] (no difference)
startup:petclinic:tracing:Agent 16.27 s 16.10 s [+0.1%; +2.0%] (maybe worse)

Commit: 9faecfb9 · CI Pipeline · Benchmarking Platform UI


Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - spring_boot

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 16.69 16.36 $\color{red}{\blacktriangle}$ +0.33 16.36 $\color{red}{\blacktriangle}$ +0.33 48/224
agentless 10.22 9.73 $\color{red}{\blacktriangle}$ +0.49 9.92 $\color{red}{\blacktriangle}$ +0.30 48/224
agentlessCodeCoverage 14.00 13.67 $\color{red}{\blacktriangle}$ +0.33 13.67 $\color{red}{\blacktriangle}$ +0.33 48/226
agentlessLineCoverage 23.53 22.54 $\color{red}{\blacktriangle}$ +0.99 22.54 $\color{red}{\blacktriangle}$ +0.99 48/224

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@cit-pr-commenter-54b7da

cit-pr-commenter-54b7da Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

CI Visibility Test Environment - sonar-java

Job Status: 🟢 success

Scenario This PR (%) 7d median Δ 7d 30d median Δ 30d runs (7d/30d)
agent 43.98 14.51 $\color{red}{\blacktriangle}$ +29.47 14.23 $\color{red}{\blacktriangle}$ +29.75 48/224
agentless 10.78 11.65 $\color{green}{\blacktriangledown}$ -0.87 13.40 $\color{green}{\blacktriangledown}$ -2.62 48/224
agentlessCodeCoverage 87.98 87.80 $\color{red}{\blacktriangle}$ +0.18 84.36 $\color{red}{\blacktriangle}$ +3.62 48/224
agentlessLineCoverage 145.88 120.92 $\color{red}{\blacktriangle}$ +24.96 123.36 $\color{red}{\blacktriangle}$ +22.52 47/223

Baseline: median of @test.tracer_overhead on main (gitlab) over the last 7/30 days, per OSS project & scenario. Δ = this PR − baseline median; red ▲ = more overhead, green ▽ = less overhead than baseline.

Tests run to verify that CI Visibility behavior has not regressed in the current PR.

@calvinbayer
calvinbayer marked this pull request as ready for review October 19, 2026 22:10
@calvinbayer
calvinbayer requested review from a team as code owners October 19, 2026 22:10
@calvinbayer
calvinbayer requested review from PerfectSlayer and ygree and removed request for a team October 19, 2026 22:10
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T22:13:14.139699Z 193ac29 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: FAIL

Protected JUnit4 tests forced to run by TIA’s unskippable category can lose their forced-run tag and metric because reporting ignores the new exclusions.

Open Bits AI session

🤖 Bits Code Review · Commit 193ac29

@calvinbayer
calvinbayer force-pushed the codex/junit4-automation-exclusions branch from 8939084 to 8028762 Compare October 20, 2026 08:09
@calvinbayer

Copy link
Copy Markdown
Author

@autotest Review

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

Source and test inspection support that protected JUnit4 tests retain blocking failures and backend assignment tags while preserving framework-owned skips and retries.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 8028762

@calvinbayer

Copy link
Copy Markdown
Author

@ygree Yes. With @PreventFailureSuppression alone, an ATR-eligible test can fail and then pass on an automatic retry. The annotation overrides Datadog disabling and quarantine; @NoAutoRetry independently disables Datadog retries, EFD and Attempt to Fix. With ATR, failure on the final attempt still blocks.

The policy selection keeps these controls independent. Your naming suggestion makes that distinction clearer; I’ll leave the API rename open for discussion.

@daniel-mohedano daniel-mohedano left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left some comments and nits, but overall it's looking good, thanks for taking care of these changes 👍

Comment thread docs/test-automation-exclusions.md Outdated
Comment thread .github/CODEOWNERS Outdated
@calvinbayer
calvinbayer requested a review from a team as a code owner October 28, 2026 09:36
@calvinbayer
calvinbayer requested review from mcculls and removed request for a team October 28, 2026 09:37
@calvinbayer

Copy link
Copy Markdown
Author

@autotest Review

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

Source inspection supports the independent retry and quarantine/disable exclusions while preserving backend assignment tags and TIA selection. Runtime behavior was not exercised.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 259ca51

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

Source review supports independent retry and failure-protection exclusions while retaining backend assignment tags. The completed static reviewer reported no actionable defects, and human PR discussion raised no additional unresolved correctness concern.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 259ca51

@mcculls
mcculls removed their request for review October 28, 2026 09:55
@calvinbayer
calvinbayer force-pushed the codex/junit4-automation-exclusions branch from 259ca51 to be2136e Compare October 28, 2026 11:31
@calvinbayer

Copy link
Copy Markdown
Author

@autotest Review

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

The exclusion controls remain independent: preventing failure suppression leaves retries available, while disabling retries preserves quarantine and disabling. The human PR discussion confirms this behavior is intentional; static review found no actionable defect.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit be2136e

@calvinbayer
calvinbayer force-pushed the codex/junit4-automation-exclusions branch from be2136e to 143fa8f Compare October 28, 2026 15:47
@calvinbayer

Copy link
Copy Markdown
Author

@autotest Review

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: FAIL

Parameterized JUnit4 display names containing nested brackets can silently bypass @NoAutoRetry and omit its exclusion telemetry because method lookup fails.

Open Bits AI session

🤖 Bits Code Review · Commit 143fa8f

@calvinbayer

Copy link
Copy Markdown
Author

@autotest Review

@datadog-datadog-prod-us1-2 datadog-datadog-prod-us1-2 Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bits Code Review: PASS

More details

Source inspection supports independent retry and failure-suppression exclusions across JUnit4 skip decisions, execution policies, and reporting, including parameterized method resolution. Runtime behavior was not exercised.

Was this helpful? React 👍 or 👎

Open Bits AI session

🤖 Bits Code Review · Commit 855c0da

@calvinbayer

Copy link
Copy Markdown
Author

Shepherd verification — JUnit4 native tests and packaged Java smoke

Tested by: Shepherd Agent (autonomous QA for Datadog Test Optimization)
Revision tested: 855c0da96cd6f320e1ffd4822492dcbb893c3ee8
Environment: local macOS arm64; packaged workload on Zulu JDK 21.

Verification Result
Native JUnit4 bracketed-parameter regression RED before the fix, GREEN after the fix, with identical final test sources
Complete JUnit4 suite and configured latest-dependency regression 62 passed; 1 existing capability-assumption skip
Spotless, CodeNarcTest, SpotBugsMain Passed
Packaged agent provenance All 17 component version resources and runtime version identify 855c0da96c
Configured Jolokia default smoke 35/35 assertions passed

The regression reproduces the annotation lookup failure for @Parameters(name="{0}") with the value [value], alongside a newline-containing label. Before the fix, the excluded failure executed four times instead of twice; the unannotated ATR control executed six times as expected. The fix restores the excluded count to two while preserving the control count, reported names, parameters, source method, and retry markers. It resolves the Java method from the first parameter separator without changing test identity formatting.

The packaged smoke used the normal Crook workflow with --debug and --dep dd-trace-java=path:<exact-head-agent.jar>. Mockdog recorded 1,769 events: 1,404 TestNG 7.12.0 tests (1,389 passed, 15 native skips), 188 suites, 32 modules, and one session. Both recorded framework tags and runtime agent version were verified. The agent SHA256 was c51abbd595d8a3c9dd9bfbde6333dec9431dbf9677f8ea4be67a27d3ffca760b.

Scope: Jolokia provides a packaged Java/TestNG smoke; the native JUnit4 instrumentation tests prove the JUnit4 annotation behavior. The configured HeliBoard JUnit4 playground could not complete normal setup because the Android SDK was absent. No SDK/NDK installation or dependency-skipping workaround was used. This verification used local Mockdog; it did not validate the Datadog UI or production backend.

Normal Crook cleanup restored the playground dependency state, removed the injected agent, and stopped its owned Mockdog process. The source worktree remained clean.

@calvinbayer
calvinbayer added this pull request to stack #13114 October 28, 2026 23:25
Resolve reflected methods before the first parameter bracket without changing
reported test names or parameter JSON. Native regression proves that bracketed
labels keep NoAutoRetry declarations and newline labels retain their behavior,
with independent body counters and an active ATR control.
@calvinbayer
calvinbayer force-pushed the codex/junit4-automation-exclusions branch from 855c0da to 5a0abf5 Compare October 30, 2026 11:04

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp: ci visibility Continuous Integration Visibility tag: ai generated Largely based on code generated by an AI or LLM type: feature Enhancements and improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants